For routines
which are not documented in an HTML manual (for example personal
or library routines), the source code itself is used as help
text. If the requested information can be found in a (more or
less) standard DocLib file header, IDLWAVE shows the header
(scrolling down to a keyword, if appropriate). Otherwise the
routine definition statement
(pro/function) is shown. The doclib
header sections which are searched for include
‘NAME’ and
‘KEYWORDS’.
Localization support can be added by customizing the
idlwave-help-doclib-name and
idlwave-help-doclib-keyword variables.
Help is also
available for class structure tags (self.TAG), and
generic structure tags, if structure tag completion is enabled
(see Structure
Tag Completion). This is implemented by visiting the tag
within the class or structure definition source itself. Help is
not available on built-in system class tags.
The help window is normally displayed in the same frame, but can be popped-up in a separate frame. The following commands can be used to navigate inside the help system for source files:
| <SPACE> | Scroll forward one
page. |
| <RET> | Scroll forward one
line. |
| <DEL> | Scroll back one page. |
| h | Jump to DocLib Header of the
routine whose source is displayed as help. |
| H | Jump to the first DocLib Header
in the file. |
| . (Dot) | Jump back and forth between the
routine definition (the
pro/function statement) and the
description of the help item in the DocLib header. |
| F | Fontify the buffer like source
code. See the variable
idlwave-help-fontify-source-code. |
| q | Kill the help window. |
nil)Non-
nilmeans use a separate frame for Online Help if possible.
The frame parameters for the special Online Help frame.
nil)Non-
nilmeans fontify source code displayed as help.
t)Non-
nilmeans try to find help in routine header when displaying source file.